Systems and methods for dynamic voice remote to control media devices

ABSTRACT

A context-driven voice-control system and method for enabling users to control customer service activities related to live broadcast programming, recorded programming, streaming programming, and on-demand programming using vocal selection by the user. The context-driven voice-control system and method may also enable users to control one or more of account management activities using vocal selection by the user, authentication to authorize changes to their account using vocal selection by the user, and troubleshooting of equipment and system capabilities using vocal selection by the user. The context-driven voice-control system and method dynamically generates and presents a list of available control and support pathways to a user based on the user attributes and the voice control requests.

TECHNICAL FIELD

The present disclosure relates to controlling media context, andparticularly to controlling media context using voice commands.

BACKGROUND

Being able to seamlessly control and watch live broadcast, recorded,streaming and on-demand programming anywhere that one has a television(TV) or mobile device is becoming an increasingly sought out feature forhome entertainment systems. One solution provides a main televisionreceiver (such as a set-top box provided by a cable or satellitetelevision service provider) that is connected to the cable or satellitetelevision service provider and that serves as the interface between thebackend cable or satellite television service provider system and thehome entertainment system on the customer premises. Connected to thistelevision receiver are a number of other receiving devices (playerdevices) each connected to respective TVs throughout the customerpremises. For example, the player devices may be connected to thetelevision receiving device via a home local area network (LAN) andcommunicate over the LAN with the television receiving device using thetransmission control protocol/Internet protocol (TCP/IP) suite ofnetworking communication protocols. These player devices are able toplay on their respective TVs the live broadcast, recorded, streaming andon-demand programming initially received by the television receivingdevice from the cable or satellite television service provider or othercontent provider.

As one example, Video on Demand (VOD) is a system which allows a user toselect, watch and/or listen to video and audio content on demand. Forexample “Internet Television” and “Internet Protocol Television” (IPTV)are systems through which various media content is delivered using theInternet protocol (IP) suite over a packet-switched network such as theInternet or a LAN, instead of being delivered through traditionalchannels using terrestrial, satellite signal, and cable televisionformats. In such situations, the device used to initially receive thecontent may be the television receiving device (e.g., set-top box)provided by the cable provider, satellite provider, or other programdistributor to which the customer subscribes for such on-demandservices. The various player devices on the customer premises incommunication with the television receiving device may also be devicesprovided by the cable provider or satellite provider. However, in someinstances, such player devices may be devices other than those providedby the cable provider or satellite provider. For example, these mayinclude various user devices such as a television, a digital videorecorder (DVR), digital versatile disc (DVD) player, personal computer(PC), tablet device, game machine, smart phone, mobile device or othercomputing device or media player not provided by or controlled by thecable provider, satellite provider, or other program distributor towhich the customer subscribes for the on-demand services.

There is also a growing desire to be able to control and watch livebroadcast, recorded, streaming and on-demand programming using voicecommands, as well as providing service, support, and troubleshootingfunctions using voice commands. However, current voice controlcapabilities are quite limited. These systems typically merely convertvoice to text and perform a generic word search, without anyintelligence or customization to individual users, accounts, or devices.As such, these current voice control systems can be very frustrating tousers and leave much to be desired.

There is a continuing need for a system that provides enhanced voicecontrol capabilities over audio/visual components and media content. Thepresent disclosure addresses this and other needs.

BRIEF SUMMARY

Briefly stated, embodiments described herein are directed towards acontext-driven voice-control system and method for enabling users tocontrol customer service activities related to live broadcastprogramming, recorded programming, streaming programming, and on-demandprogramming using vocal selection by the user. In other embodiments, thecontext-driven voice-control system and method enables users to controlone or more of account management activities using vocal selection bythe user, authentication to authorize changes to their account usingvocal selection by the user, and troubleshooting of equipment and systemcapabilities using vocal selection by the user.

In one or more embodiments, a method for context-driven voice-controlusing an application control interface, includes gathering userattributes for use in a voice control session; receiving a voice controlrequest from a user during the voice control session; dynamicallygenerating and presenting a list of available control and supportpathways to a user based on the user attributes and the voice controlrequests; in response to a vocal selection by a user of an availablecontrol and support pathways, presenting stages sequentially to theuser, each stage having a list of actions that the user can select tofacilitate resolution to the user's voice control request; in responseto receiving a vocal selection of an action in the voice controlsession, updating the stages sequentially presented to the user in theavailable control and support pathways to facilitate resolution to theuser's voice control request; and in response to receiving a vocalselection of an action in the voice control session, sending anauthorization signal via an external system to perform a functionrelated to the vocally selected action.

In some embodiments, user attributes include one or more of packagessubscribed to by the user, tenure of the user, payment history of theuser, user equipment undergoing troubleshooting, and the like. Inanother aspect of some embodiments, the method also includes enablingusers to add a support application via a voice assistant associatedapplication store. In still another aspect of some embodiments, themethod further includes, authenticating the user to enable accountspecific features, after installation of the voice assistant associatedapplication. In yet another aspect of some embodiments, the methodfurther includes, prompting users with a standard greeting and askingusers to provide a description of a current issue of interest to theuser. In other aspects of some embodiments, the method further includesreceiving the vocal selection by the user of a search result that mostclosely matches the current issue of interest to the user.

In other embodiments, a context-driven voice-control system using anapplication control interface includes one or more processors and amemory device storing a set of instructions that, when executed by theone or more processors, causes the one or more processors to: gatheruser attributes for use in a voice control session; receive a voicecontrol request from a user during the voice control session;dynamically generate and present a list of available control and supportpathways to a user based on the user attributes and the voice controlrequests; in response to a vocal selection by a user of availablecontrol and support pathways, present stages sequentially to the user,each stage having a list of actions that the user can select tofacilitate resolution to the user's voice control request; in responseto receiving a vocal selection of an action in the voice controlsession, update the stages sequentially presented to the user in theavailable control and support pathways to facilitate resolution to theuser's voice control request; and, in response to receiving a vocalselection of an action in the voice control session, send anauthorization signal via an external system to perform a functionrelated to the vocally selected action.

In some embodiments, the system verbally leads the user along a controland support pathway to resolve a customer service issue with sequentialstages, each stage having a list of vocally selectable actions by theuser. In another aspect of some embodiments, the system enables users toskip stages or add additional stages based on logic defined by one ormore of user attributes and the vocal selections by the user. In stillanother aspect of some embodiments, the system records stages taken andactions selected by the user on the control and support pathway, uponcompletion of the vocally selected control and support pathway. In yetanother aspect of some embodiments, the system leverages the record ofstages taken and actions selected by the user for future use withtechnical support to help expedite troubleshooting.

In some embodiments of the context-driven voice-control system, if theuser's voice control request has not been resolved, the system providesescalation paths that include one or more of: present a customer supportphone number, present a customer support email address, and offer toconnect the user with a live agent. In another aspect of someembodiments of the context-driven voice-control system, visibility ofavailable control and support pathways to the user is driven bypermissions to access rights of the user. In still another aspect ofsome embodiments, the context-driven voice-control system furtherincludes a context manager that manages permissions and logic sets. Thepermissions control the visibility of available control and supportpathways to the user and category visibility to the user. The logic setscontrol action visibility to the user. In yet another aspect of someembodiments, the context-driven voice-control system also includes usinga front end user interface that enables users to identify an appropriatecontrol and support pathway that addresses a current issue of interestto the user via browsing a list of available control and supportpathways to the user.

In still other embodiments, a method for context-driven voice-controlusing an application control interface includes: enabling a user toinitiate a voice control session; gathering user attributes for use inthe voice control session; receiving voice control requests from a userduring the voice control session; executing a search and dynamicallygenerating control and support pathways that are available to a userbased on the user attributes; presenting a list of available control andsupport pathways to a user based on the user attributes and the voicecontrol requests; receiving a vocal selection, by the user, of anavailable control and support pathway; after the available control andsupport pathway is vocally selected, presenting stages sequentially tothe user, each stage having a list of actions that the user can select;in response to receiving a vocal selection of an action in the voicecontrol session, updating the stages sequentially presented to the userin the available control and support pathway; and in response toreceiving a vocal selection of an action in the voice control session,sending an authorization signal via an external system to perform afunction related to the vocally selected action.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The components in the drawings are not necessarily to scale relative toeach other. Like reference numerals designate corresponding partsthroughout the several views.

FIG. 1 is a logical flow diagram illustrating the rules engine of thecontext-driven voice-control system and method, according to one exampleembodiment.

FIG. 2 is an example of the system architecture for the context-drivenvoice-control system and method, according to one example embodiment.

FIG. 3 is an overview block diagram illustrating an example contentdistribution environment in which a context-driven voice-control systemand method may operate, according to one example embodiment.

FIG. 4 is a block diagram illustrating elements of an example receivingdevice used in a context-driven voice-control system and method,according to one example embodiment.

DETAILED DESCRIPTION

Each of the features and teachings disclosed herein may be utilizedseparately or in conjunction with other features and teachings toprovide a context-driven voice-control system and method 100.Representative examples utilizing many of these additional features andteachings, both separately and in combination, are described in furtherdetail with reference to the attached FIGS. 1-4. This detaileddescription is intended to teach a person of skill in the art furtherdetails for practicing aspects of the present teachings and is notintended to limit the scope of the claims. Therefore, combinations offeatures disclosed in the detailed description may not be necessary topractice the teachings in the broadest sense, and are instead taughtmerely to describe particularly representative examples of the presentteachings.

In some embodiments, the context-driven voice-control system and method100 includes an application program interface that enables users tocontrol certain customer service activities with respect to livebroadcast, recorded, streaming and on-demand programming using vocalcommands in a customer service control system. To support this voicecontrol system, a user adds a voice support application via a voiceassistant application store or via other methods supported by theirplatform to their receiving device, remote control, mobile device, orplayer device. After installation of this voice support application, theuser authenticates itself with the context-driven voice-control systemto enable account specific features. In one or more implementations,users are prompted with a standard greeting when initiating a voicecontrol session.

Referring to FIG. 1, the context-driven voice-control system and method100 also obtains and establishes many user attributes at the beginningof a voice control session, at 110. In various embodiments, a voicecontrol session may be initiated using the receiving device, remotecontrol, mobile device, or player device to capture the user's voice.These attributes include, by way of example only, and not by way oflimitation: channels subscribed to by the user, types of voice controlrequest that can be taken, length of time as a user, user status (e.g.,VIP, star rating, or other elevated status), promotional offersavailable to the user account, equipment on the user account, andline(s) of business associated with the user. In some embodiments, theseuser attributes defined at the beginning of the voice control sessiondetermine which control and support pathways are available to users viavoice control, as well as what categories are available to users viavoice control, at 120. These available control and support pathways arethen presented to the user. The user's attributes established during thevoice control session and the user's last actions are evaluated by arules engine, at 130. In some embodiments, the rules engine is poweredby a binary expression tree. The results are utilized to determine whatactions are available to the user, as well as what stages in the controland support pathways are visible to the user.

At this point, in one example of the context-driven voice-control system100 shown in FIG. 1, three different control and support pathways 140,150, and 160 are possible, depending on the attributes of the user. Inthis embodiment, if the user has attributes that include the channelsubscription for the History Channel, then control and support pathway140 is selected and the message “Please tune to the History Channel now”is displayed, at 148, on a presentation device (e.g., television). Inanother embodiment, the presentation device (e.g., television) mayautomatically have the channel switched to the History Channel by acommand from the system 100. Continuing, if the user has attributes thatdo not include the channel subscription of the History Channel, then thecontrol and support pathway 150 is selected and the message “Please tuneto the TBS channel now” is displayed, at 158, on a presentation device(e.g., television). In another embodiment, the presentation device(e.g., television) may automatically have the channel switched to theTBS channel by a command from the system 100. Finally, in thisembodiment, if the user has attributes that do not include the channelsubscription of the History Channel, but the user has a Hopper 3, and astar rating of 4 stars or above, then the control and support pathway160 is selected and the message “Office to add the History Channel freeof charge” is displayed, at 168, on a presentation device (e.g.,television). It should be noted that in this embodiment, only the userattributes were used to determine what control and support pathways wereavailable to the user. In other embodiments, both the user attributesand the voice control request of the user are used to determine whatcontrol and support pathways were available to the user.

In another aspect of some embodiments, the context-driven voice-controlsystem 100 then asks the user to provide a description of current issueof interest. After receiving a response from the user to this inquiry,the context-driven voice-control system 100 executes a search using arules engine is powered by a binary expression tree, and then provides alist of available control and support pathways to the user as results.After reviewing the list of results, the user selects an availablecontrol and support pathway from the list of results that most closelymatches the issue they are experiencing. The context-drivenvoice-control system 100 then verbally leads the user along a controland support pathway to resolve a customer service issue with sequentialstages.

Notably, the context-driven voice-control system and method 100 providesa list of available control and support pathways that is dynamicallydriven by context. The user of the context-driven voice-control system100 then vocally selects an available control and support pathway thatbest addresses the user's issue (e.g., television signal is “fuzzy,”trouble switching input signal, trouble with audio signal, trouble withdisplay parameters, trouble with closed captioning, trouble searchingprogramming, and the like). After the available control and supportpathway is vocally selected by the user, the context-drivenvoice-control system 100 presents stages sequentially to the user. Eachstage has a list of actions that the user can select to help resolve thecurrent user issue. In response to receiving a vocal selection of anaction in the voice control session, the context-driven voice-controlsystem 100 updates the stages that are sequentially presented to theuser. Additionally, the context-driven voice-control system 100 may alsosend an authorization signal via an external system to perform afunction related to the vocally selected action, in response toreceiving a vocal selection of an action in the voice control session.In one aspect of some embodiments, the context-driven voice-controlsystem and method 100 may enable the users to skip stages or addadditional stages based on logic defined by a context management teamusing the user's attributes.

In one or more embodiments, the context-driven voice-control system andmethod 100 includes a user front end interface that enables agents orcustomers to quickly identify an appropriate control and support pathwaythat fits with the issue that the user is facing by searching a list ofavailable support pathways. Notably, the available control supportpathways and categories are dynamic generated, meaning that theavailable control support pathways and categories presented to the uservary depending on the user's attributes, as well as the voice controlrequest made by the user. In one or more embodiments, visibility of theavailable control and support pathways presented on the results list isdriven by permissions created by the context-driven voice-control system100. The permissioning system of the context-driven voice-control system100 is configured to support any number of data sources, which drivesrules on rights accessibility.

Once a control and support pathways is vocally selected in thecontext-driven voice-control system 100, stages are presented one at atime to the user. Each stage includes a list of actions that the usercan select. Notably, in some embodiments of the context-drivenvoice-control system 100, actions in the control and support pathwaysthat are available to the user are dynamically generated based on userattributes gathered in that session (e.g., packages subscribed to by theuser, tenure of the user, payment history of the user, user equipmentundergoing troubleshooting, and the like). In this manner, the actionvocally selected by the user determines what the next available actionspresented on the user front end interface will be. Additionally, theaction vocally selected by the user determines what stage is be shownnext to the user. In another aspect of context-driven voice-controlsystem 100, actions also have the ability to perform additionalfunctions beyond determining what stage to show next, as well asinterface with external systems. For example, in some embodiments, anaction sends an authorization signal via an external system, as well asdelivering the user to the next stage in the process. As discussedabove, control and support pathways that are available to the user aredynamically generated based on user attributes gathered. Upon completionof the support pathway, all stages performed by the user are saved tothe appropriate system, depending on the type of interaction.

In some embodiments, the context-driven voice-control system 100includes an administrator/context manager front end interface thatenables context managers to create, manage, and update all aspects ofthe context-driven voice-control system's context. In addition tocreating new control and support pathways, context managers are alsoable to manage both permissions (e.g., controlling control and supportpathways and category visibility) and logic sets (e.g., controllingaction visibility) via an administration tool. The service layer of thecontext-driven voice-control system and method 100 contains allfunctions needed by both front end interfaces (i.e., user front endinterface and administrator/context manager front end interface) tooperate.

In some embodiments, upon completion of the support pathway by thecontext-driven voice-control system and method 100, internal records areupdated with a note of stages selected by the user on the control andsupport pathway. In such an embodiment, this record is visible forfuture use with technical support to help expedite troubleshooting. Uponcompletion of the control and support pathway by the user in thecontext-driven voice-control system and method 100, the user may beprompted to confirm resolution of the issue. Alternatively, if the issuehas not been resolved, escalation paths may be presented to the user.Such escalation paths may include providing a customer support phonenumber, providing a customer support email address, or offering toconnect the user with a live agent.

Referring now to FIG. 2, an example system architecture for thecontext-driven voice-control system and method is shown. In suchembodiments, the context-driven voice-control system and method 100includes a tech stack that is an internally facing single pageapplication (SPA) built using Angular framework for agents. In one ormore embodiments, the internally facing single page application isaccess controlled using Angular framework for administrators and contextmanagers. In some embodiments, a WebAPI RESTful service layer is builtusing .Net Core. The service layer may be designed using an “API first”based methodology that allows the voice assistant ApplicationProgramming Interface (API) 210 to be used with any front end (e.g., webapplications, mobile applications, voice assistants, voice controlledremote controller, etc.). In such embodiments, the layers of the toolare cloud deployed via Amazon Web Services or other appropriate cloudservice provider (e.g., the information provider 338 in FIG. 3).

As shown in FIG. 2, a voice assistance user 202 may use a voiceassistance API 210 to connect to a virtual private cloud 220. Thevirtual private cloud 220 in turn connects through a cloud transitgateway 230 to a plurality of virtual servers (e.g., Elastic ComputerClouds; EC2s) 250, 254, and 258. The virtual servers 250, 254, and 258each have respective Application Load Balancer (ALB) 240, 244, 248. Thevirtual server 250 has instances that include a frontend auto-scalinggroup and a frontend target group. The virtual server 254 has instancesthat include an admin auto-scaling group and an admin target group. Thevirtual server 258 has instances that include an API auto-scaling groupand an API target group. The virtual servers further connect toadditional cloud transit gateways 260 and virtual private cloud 270.

Referring now to FIG. 3, an overview block diagram is shown illustratingan example content distribution environment 302 in which embodiments ofthe context-driven voice-control system and method 100 may beimplemented, according to one or more embodiments. In addition toproviding details regarding the operation and constitution of thecontext-driven voice-control system and method 100, the example contentdistribution environment 302, within which such a system may operate,will briefly be described.

In the content distribution environment 302, audio, video, and/or dataservice providers, such as television service providers, provide theircustomers a multitude of video and/or data programming (herein,collectively “programming”). Such programming is often provided by useof a receiving device 318 (e.g., in some embodiments referred to as ahopper) communicatively coupled to a presentation device 320 configuredto receive the programming. In one or more embodiments, the receivingdevice 318 is dynamically controlled by the context-driven voice-controlsystem and method 100. The dynamic nature of this voice control refersto how the actions in the control and support pathways that areavailable to the user are dynamically generated based on user attributesgathered in that session. The programming may include any type of mediacontent, including, but not limited to: television shows, news, movies,sporting events, advertisements, etc. In various embodiments, any ofthis programming may be provided as a type of programming referred to asstreaming media content, which is generally digital multimedia data thatis substantially constantly received by and presented to an end-user orpresented on a device while being delivered by a provider from a storedfile source. Its verb form, “to stream,” refers to the process ofdelivering media in this manner. The term refers to how the media isdelivered rather than the media itself.

The receiving device 318, which may be dynamically controlled by thecontext-driven voice-control system and method 100, interconnects to oneor more communications media or sources. For example, the various mediacontent may be delivered as data using the IP suite over apacket-switched network such as the Internet or other packet-switchednetwork. The underlying connection carrying such data may be via a cablehead-end, satellite antenna, telephone company switch, cellulartelephone system, Ethernet portal, off-air antenna, or the like. Thereceiving device 318 may receive a plurality of programming by way ofthe communications media or sources, or may only receive programming viaa particular channel or source described in greater detail below. Insome embodiments, based upon selection by a user, the receiving device318 processes and communicates the selected programming to thepresentation device 320. Also, in some embodiments, the presentationdevice 320 may also be a receiving device 318 or have a receiving device318 integrated within it.

Examples of a receiving device 318 may include, but are not limited to,devices such as, or any combination of: a “television converter,”“receiver,” “set-top box,” “television receiving device,” “televisionreceiver,” “television,” “television recording device,” “satelliteset-top box,” “satellite receiver,” “cable set-top box,” “cablereceiver,” “media player,” “digital video recorder (DVR),” “digitalversatile disk (DVD) Player,” “computer,” “mobile device,” “tabletcomputer,” “smart phone,” “MP3 Player,” “handheld computer,” and/or“television tuner,” etc. Accordingly, the receiving device 318 may beany suitable converter device or electronic equipment that is operableto receive programming via a connection to a satellite or cabletelevision service provider outside the customer premises andcommunicate that programming to another device over a network. Further,the receiving device 318 may itself include user interface devices, suchas buttons or switches. In some example embodiments, the receivingdevice 318 may be configured to receive and decrypt content according tovarious digital rights management (DRM) and other access controltechnologies and architectures.

Examples of a presentation device 320 may include, but are not limitedto, one or a combination of the following: a television (“TV”), apersonal computer (“PC”), a sound system receiver, a digital videorecorder (“DVR”), a compact disk (“CD”) device, DVD Player, game system,tablet device, smart phone, mobile device or other computing device ormedia player, and the like. Presentation devices 320 employ a display,one or more speakers, and/or other output devices to communicate videoand/or audio content to a user. In many implementations, one or morepresentation devices 320 reside in or near a customer's premises 316 andare communicatively coupled, directly or indirectly, to the receivingdevice 318. Further, the receiving device 318 and the presentationdevice 320 may be integrated into a single device. Such a single devicemay have the above-described functionality of the receiving device 318and the presentation device 320, or may even have additionalfunctionality.

In the example embodiment shown in FIG. 3, a plurality of player devices328 a, 328 b, 328 n (e.g., wireless Joeys, which are remote media playerdevices) are communicatively connected to the television receivingdevice via a home LAN 336 that generally covers only part or all of thecustomer premises 316. In one or more embodiments, the plurality ofplayer devices 328 a, 328 b, 328 n are dynamically controlled by thecontext-driven voice-control system and method 100. There may be feweror additional player devices in various embodiments. Each of the playerdevices 328 a, 328 b, 328 n communicates over the LAN 336 with thetelevision receiving device using the transmission controlprotocol/Internet protocol (TCP/IP) suite of networking communicationprotocols. In various embodiments, all or part of the LAN 336 may bewired or wireless. These player devices are able to receive from thereceiving device 318, over LAN 336, and play on their respectiveconnected presentation devices 340, 342, 344, the live broadcast,recorded, streaming and/or on-demand programming initially received bythe receiving device 318 from the cable or satellite television serviceprovider. In the present example, the cable or satellite televisionservice provider may encompass or be in communication with some or allof the content provider 304, program distributor 306, content storagesystem of content delivery network 322, and/or information provider 338.

Television VOD systems may stream content to a receiving device 318 suchas a set-top box, DVD player, game system, smart phone, television(including a smart TV), PC, a sound system receiver, a digital videorecorder (“DVR”), a compact disk (“CD”) device, tablet device, mobiledevice or other computing device or media player, and the like, allowingviewing in real time at the customer premises 316, or download it to areceiving device 318 such as a computer, DVR (also called a personalvideo recorder) or portable media player for viewing at any time. Thereceiving device 318 may in turn provide each of the player devices 328a, 328 b, 328 n access to such content from the receiving device 318over the home LAN 336, such that each player device 328 a, 328 b, 328 nmay play the content on their respective connected presentation devices340, 342, 344, at various locations throughout the customer premises316. In some embodiments, the presentation device may be integrated aspart of the player device. Also, in some embodiments, a player devicemay communicate with the receiving device 318 to receive such contentremotely via the Internet or otherwise via communication system 308. Theprogram distributor 306 may offer VOD streaming, including pay-per-viewand free content, whereby a user buys or selects a movie or televisionprogram and it begins to play on the presentation device 320 or on otherpresentation devices 340, 342, 344 via their respective player devices328 a, 328 b, 328 n almost instantaneously, downloading of the mediacontent to a DVR rented from the program distributor, and/or downloadingthe content onto a computer or mobile device, for viewing in the future.

In some embodiments, the receiving device 318 may be a set-top box thatis typically provided by the cable provider, satellite provider, orother program distributor 306 to which the customer may subscribe toreceive such on-demand services and that also receives programmingthrough traditional channels using a terrestrial, satellite signal,and/or cable television format. The various player devices 328 a, 328 b,328 n on the customer premises in communication with the receivingdevice 318 may also be devices provided by the cable provider orsatellite provider. However, in some instances, such player devices maybe devices other than those provided by the cable provider or satelliteprovider. For example, these may include various user devices such as atelevision, a digital video recorder (DVR), digital versatile disc (DVD)player, personal computer (PC), tablet device, game machine, smartphone, mobile device or other computing device or media player notprovided by or controlled by the cable provider, satellite provider, orother program distributor to which the customer subscribes for theon-demand services.

FIG. 4 is a block diagram illustrating elements of an example receivingdevice 318 used in the context-driven voice-control system and method100, according to one example embodiment. In one embodiment, thereceiving device 318 is a device such as a set-top box, television, DVR,DVD player, PC, tablet device, game machine, smart phone, mobile deviceor other computing device or media player configured to receiveprogramming via a connection to a satellite or cable television serviceprovider outside the customer premises and to display such programmingon a presentation device. For example, the receiving device 318 may beconfigured to receive, process and display on a presentation devicestreaming media content received directly from the satellite or cabletelevision service provider and/or other programming received directlyfrom the satellite or cable television service provider such as cable orsatellite television broadcasts via various other physical and logicalchannels of communication.

In the embodiment shown in FIG. 4, receiving device 318 comprises acomputer memory (“memory”) 401, a display 402 (including, but notlimited to, a light emitting diode (LED) panel, cathode ray tube (CRT)display, liquid crystal display (LCD), touch screen display, etc.), oneor more Central Processing Units (“CPU”) 403, other Input/Output (“I/O”)devices 404 (e.g., keyboard, mouse, microphone, RF or infrared receiver,universal serial bus (USB) ports, other communication ports, voicecontrolled remote controller, and the like), other computer-readablemedia 405, and network connections 406. The receiving device operationmanager 422 is shown residing in memory 401. In other embodiments, someportion of the contents and some, or all, of the components of thereceiving device operation manager 422 may be stored on and/ortransmitted over the other computer-readable media 405. The componentsof the receiving device 318 and operation manager 422 (which may includethe rules engine) preferably execute on one or more CPUs 403 to: gatheruser attributes for use in a voice control session; receive a voicecontrol request from a user during the voice control session;dynamically generate and present a list of available control and supportpathways to a user based on the user attributes and the voice controlrequest; in response to a vocal selection by a user of an availablecontrol and support pathway, present stages sequentially to the user,each stage having a list of actions that the user can select tofacilitate resolution to the user's voice control request; in responseto receiving a vocal selection of an action in the voice controlsession, update the stages sequentially presented to the user in theavailable control and support pathways to facilitate resolution to theuser's voice control request; and in response to receiving a vocalselection of an action in the voice control session, send anauthorization signal via an external system to perform a functionrelated to the vocally selected action. In other embodiments, the rulesengine may be implemented by the Information Provider 338, ProgramDistributor 306, or some other backend system.

In some embodiments, the receiving device 318 and operation manager 422include an API (as previous described and as shown in FIG. 2) thatprovides programmatic access to one or more functions of the receivingdevice 318 and operation manager 422. For example, such an API mayprovide a programmatic interface to one or more functions of thereceiving device operation manager 422 that may be invoked by one of theother programs 430, a remote control (not shown), the programdistributor 306, the content provider 304, information provider 338,content storage system of the content delivery network 322 or some othermodule. In this manner, the API may facilitate the development ofthird-party software, such as various different on-demand serviceapplications, user interfaces, plug-ins, adapters (e.g., for integratingfunctions of the receiving device operation manager 422 and informationprovider 338 into desktop applications), and the like to facilitatecontext-driven voice-control of the receiving device 318.

Referring again to FIGS. 1 and 2, in some embodiments of thecontext-driven voice-control system 100, logic sets, rules, and actionsare all evaluated and shown on the front end interface as a userproceeds through a control and support pathway. When creating acategory, the context-driven voice-control system and method 100 is ableto associate an existing control and support pathway (and its subset ofstages) to the category instead of having to create a new control andsupport pathway. A category can be associated to different lines ofbusinesses. Types of categories may include, by way of example only, andnot by way of limitation, troubleshooting, audio, video, channelselection, input selection, and the like.

In another aspect of the context-driven voice-control system 100, asection of “categories” are presented to assist with navigating to asingle control and support pathway to begin troubleshooting or othertypes of support or control functions. Main categories are immediatelydisplayed in the categories section, while selectable subcategories areseen beneath the main categories until only a single control and supportpathway is available to choose. In some embodiments, the context-drivenvoice-control system 100 also includes categories and/or control andsupport pathways without equipment based permission sets so that usersmay receive assistance with customer service based issues without extraunnecessary stages.

In one or more embodiments, the context-driven voice-control system 100includes logic statements that encompass many different use cases tosolve problems without the assistance of an information technologydepartment. In another aspect, the context-driven voice-control systemand method 100 has control and support pathways and included stagesbased on any number of different filters to determine how each filter isbeing utilized. Filters attached to each control and supportpathways/stage are visible in an administration/context manager (e.g.,all stages tied to a Hopper 3 receiver, all control and support pathwaysthat can be troubleshot by a T3 agent, and the like). In someembodiments, the administration/context manager may be included in orexecuted by the Receiving Device Operation Manager 422 or Other Programs430 of FIG. 4.

Notably, in some embodiments, the context-driven voice-control system100 is able to group stages so that many applicable stages can be addedwith a single selection. This functionality enables stages to be groupedunder their core name and versioning. For example, there may be 15different versions for the stage “Does Resetting the Receiver Resolvethe Issue” because these versions are broken out by distinct receivermodel. In another aspect of one or more embodiments, the context-drivenvoice-control system 100 retrieves the customer's line of business, aswell as the devices associated with the line of business, so that atechnical support portal can display the appropriate control and supportpathways to troubleshoot. Additionally, the context-driven voice-controlsystem 100 may retrieve the customer's type of account so that thetechnical support portal can display the appropriate control and supportpathways to troubleshoot.

In other aspects of some embodiments, the context-driven voice-controlsystem 100 records the number of selections made per action so that thisinformation is available to aid in sorting decisions. For example, “Yes”or “No” is an “action” to the question “Does resetting the receiverresolve the issue?” Furthermore, the context-driven voice-control system100 also records additional data not already accounted for to provideinformation to the data warehouse tables. Such data collection mayinclude: end call type codes, call completion stage, receiver number,hash code field for pop-ups, indicate when a control and support pathwayare initiated from a pop-up with the pop-up number and hash value, andindicate when a new control and support pathway is started after one hasbeen completed on the same call.

In still another aspect of some embodiments, the context-drivenvoice-control system 100 retrieves potential known issues impacting thecustomer to prevent unnecessary troubleshooting. Such informationretrieval stages may include: (1) retrieve receiver model in control andsupport pathway tool; (2) retrieve category of control and supportpathway in KI tool to category in control and support pathway tool; (3)pull the number of the known issue, description of the known issue aswell as work around description; and (4) retrieve core programmingpackages, premiums, add-ons, locals, RS Nets, international, SVOD(Subscription based Video On Demand), IP Live Linear, PPV (Pay Per View)to compare to Services.

As described above, some embodiments of the context-driven voice-controlsystem 100 include a context manager that employs permissions thatencompass many different use cases, and controls the visibility ofavailable control and support pathways to the user and categoryvisibility to the user. The context manager may also manage logic setsthat control action visibility to the user so that only the applicableactions will appear. In some embodiments, the context-drivenvoice-control system 100 has a back end agent interface that displaysheader information for each agent facing pop-up/slate/issue. This headerinformation provides more context regarding what caused this issue forthe user.

In some embodiments, the context-driven voice-control system 100 is ableto associate a default logic set to a stage so that the logic set willautofill in when adding the stage to a control and support pathway.Advantageously, when using the context-driven voice-control system andmethod 100, potential product known issues are displayed based on therelevant line or business, device/equipment, and category that has beenselected. Potential known service issues may be displayed based on thespecific programming the customer has, such as PPV (pay-per-view).Additionally, “On Demand” content that is available to bepurchased/streamed is presented to anyone who can potentiallypurchase/download it.

In one or more embodiments, the context-driven voice-control system 100reveals the first attribute matching stage in a control and supportpathway that is applicable to the attributes that are selected. Forexample, if a Hopper 3 device is chosen and the first stage in thecontrol and support pathway is associated to only VIP receivers, but thesecond stage in the control and support pathway is associated to aHopper 3 device, then the control and support pathway will begin atstage two, since this is the first attribute matching stage.

In still another aspect of some embodiments, the context-drivenvoice-control system 100 enables a user who has recently been assistedvia technical support portal to resume the control and support pathwaythat the user was last visiting to offer a streamlined experience forthe user. For example, the system provides the option to resume thecontrol and support pathway if the same user accesses the system for thesame problem within 48 hours. In another example, if a user who wasrecently served by the context-driven voice-control system 100 returnswithin seven days and did not completed the previous control and supportpathway, the system prompts the user to resume the previous control andsupport pathway.

Referring again to FIG. 4, components/modules of the receiving device318, which is dynamically controlled by the context-driven voice-controlsystem and method 100, and operation manager 422 are implemented usingstandard programming techniques. For example, the receiving deviceoperation manager 422 may be implemented as a “native” executablerunning on the CPU 403, along with one or more static or dynamiclibraries. In other embodiments, the receiving device 318 and operationmanager 422 may be implemented as instructions processed by a virtualmachine that executes as one of the other programs 430. In general, arange of programming languages known in the art may be employed forimplementing such example embodiments, including representativeimplementations of various programming language paradigms, including butnot limited to, object-oriented (e.g., Java, C++, C#, Visual Basic.NET,Smalltalk, and the like), functional (e.g., ML, Lisp, Scheme, and thelike), procedural (e.g., C, Pascal, Ada, Modula, and the like),scripting (e.g., Perl, Ruby, Python, JavaScript, VBScript, and thelike), or declarative (e.g., SQL, Prolog, and the like).

In a software or firmware implementation, instructions stored in amemory configure, when executed, one or more processors of the receivingdevice 318 to perform the functions of the receiving device operationmanager 422. In one embodiment, instructions cause the CPU 403 or someother processor, such as an I/O controller/processor, to: gather userattributes for use in a voice control session; receive a voice controlrequest from a user during the voice control session; dynamicallygenerate and present a list of available control and support pathways toa user based on the user attributes and the voice control request; inresponse to a vocal selection by a user of an available control andsupport pathway, present stages sequentially to the user, each stagehaving a list of actions that the user can select to facilitateresolution to the user's voice control request; in response to receivinga vocal selection of an action in the voice control session, update thestages sequentially presented to the user in the available control andsupport pathways to facilitate resolution to the user's voice controlrequest; and in response to receiving a vocal selection of an action inthe voice control session, send an authorization signal via an externalsystem to perform a function related to the vocally selected action.

The embodiments described above may also use well-known or othersynchronous or asynchronous client-server computing techniques. However,the various components may be implemented using more monolithicprogramming techniques as well, for example, as an executable running ona single CPU computer system, or alternatively, decomposed using avariety of structuring techniques known in the art, including but notlimited to, multiprogramming, multithreading, client-server, orpeer-to-peer, running on one or more computer systems each having one ormore CPUs or other processors. Some embodiments may execute concurrentlyand asynchronously, and communicate using message passing techniques.Equivalent synchronous embodiments are also supported by a receivingdevice operation manager 422 implementation. Also, other functions couldbe implemented and/or performed by each component/module, and indifferent orders, and by different components/modules, yet still achievethe functions of the receiving device 318 and operation manager 422.

In addition, programming interfaces to the data stored as part of thereceiving device 318 and operation manager 422 can be available bystandard mechanisms such as through C, C++, C#, and Java APIs; librariesfor accessing files, databases, or other data repositories; scriptinglanguages such as XML; or Web servers, FTP servers, NFS file servers, orother types of servers providing access to stored data. The mediacontent storage 416 and other data 420 may be implemented as one or moredatabase systems, file systems, or any other technique for storing suchinformation, or any combination of the above, including implementationsusing distributed computing techniques.

Different configurations and locations of programs and data arecontemplated for use with techniques described herein. A variety ofdistributed computing techniques are appropriate for implementing thecomponents of the illustrated embodiments in a distributed mannerincluding but not limited to, TCP/IP sockets, RPC, RMI, HTTP, and WebServices (XML-RPC, JAX-RPC, SOAP, and the like). Other variations arepossible. Other functionality could also be provided by eachcomponent/module, or existing functionality could be distributed amongstthe components/modules in different ways, yet still achieve thefunctions of the receiving device operation manager 422.

Furthermore, in some embodiments, some or all of the components of thereceiving device 318 and operation manager 422 may be implemented orprovided in other manners, such as at least partially in firmware and/orhardware, including, but not limited to, one or moreapplication-specific integrated circuits (“ASICs”), standard integratedcircuits, controllers (e.g., by executing appropriate instructions, andincluding microcontrollers and/or embedded controllers),field-programmable gate arrays (“FPGAs”), complex programmable logicdevices (“CPLDs”), and the like. Some or all of the system componentsand/or data structures may also be stored as contents (e.g., asexecutable or other machine-readable software instructions or structureddata) on a computer-readable medium (e.g., as a hard disk; a memory; acomputer network, cellular wireless network or other data transmissionmedium; or a portable media article to be read by an appropriate driveor via an appropriate connection, such as a DVD or flash memory device)so as to enable or configure the computer-readable medium and/or one ormore associated computing systems or devices to execute or otherwiseuse, or provide the contents to perform, at least some of the describedtechniques.

While various embodiments have been described herein above, it is to beappreciated that various changes in form and detail may be made withoutdeparting from the spirit and scope of the invention(s) presently orhereafter claimed.

1. A method for context-driven voice-control using an application control interface, the method comprising: gathering user attributes for use in a voice control session; receiving a voice control request from a user during the voice control session; dynamically generating and presenting a list of available control and support pathways to a user based on the user attributes and the voice control request; in response to a vocal selection by a user of an available control and support pathway, presenting stages sequentially to the user, each stage having a list of actions that the user can select to facilitate resolution to the user's voice control request; in response to receiving a vocal selection of an action in the voice control session, updating the stages sequentially presented to the user in the available control and support pathways to facilitate resolution to the user's voice control request; and in response to receiving a vocal selection of an action in the voice control session, sending an authorization signal via an external system to perform a function related to the vocally selected action.
 2. The method of claim 1, further comprising: enabling users to control customer service activities related to live broadcast programming, recorded programming, streaming programming, and on-demand programming using vocal selection by the user.
 3. The method of claim 1, further comprising: enabling users to control account management activities using vocal selection by the user.
 4. The method of claim 1, further comprising: enabling users to control authentication to authorize changes to their account using vocal selection by the user.
 5. The method of claim 1, further comprising: enabling users to control troubleshooting of equipment and system capabilities using vocal selection by the user.
 6. The method of claim 1, wherein user attributes include one or more of packages subscribed to by the user, tenure of the user, payment history of the user, user equipment undergoing troubleshooting, and the like.
 7. The method of claim 1, further comprising: enabling users add a support application via a voice assistant associated application store.
 8. The method of claim 7, further comprising: after installation of the voice assistant associated application, authenticating the user to enable account specific features.
 9. The method of claim 1, further comprising: prompting users with a standard greeting and asking users to provide a description of a current issue of interest to the user.
 10. The method of claim 9, wherein receiving a vocal selection, by the user, of an available control and support pathway, further includes receiving the vocal selection by the user of a search result that most closely matches the current issue of interest to the user.
 11. A context-driven voice-control system using an application control interface, the system comprising: one or more processors; and a memory device storing a set of instructions that, when executed by the one or more processors, causes the one or more processors to: gather user attributes for use in a voice control session; receive a voice control request from a user during the voice control session; dynamically generate and present a list of available control and support pathways to a user based on the user attributes and the voice control requests; in response to a vocal selection by a user of an available control and support pathway, present stages sequentially to the user, each stage having a list of actions that the user can select to facilitate resolution to the user's voice control request; in response to receiving a vocal selection of an action in the voice control session, update the stages sequentially presented to the user in the available control and support pathways to facilitate resolution to the user's voice control request; and in response to receiving a vocal selection of an action in the voice control session, send an authorization signal via an external system to perform a function related to the vocally selected action.
 12. The system of claim 11, wherein the memory device further stores a set of instructions that, when executed by the one or more processors, causes the one or more processors to: verbally lead the user along a control and support pathway to resolve a customer service issue with sequential stages, each stage having a list of vocally selectable actions by the user.
 13. The system of claim 11, wherein the memory device further stores a set of instructions that, when executed by the one or more processors, causes the one or more processors to: enable the users to skip stages or add additional stages based on logic defined by one or more of user attributes and the vocal selections by the user.
 14. The system of claim 11, wherein the memory device further stores a set of instructions that, when executed by the one or more processors, causes the one or more processors to: record stages taken and actions selected by the user on the control and support pathway, upon completion of the vocally selected control request and control and support pathway.
 15. The system of claim 14, wherein the memory device further stores a set of instructions that, when executed by the one or more processors, causes the one or more processors to: leverage the record of stages taken and actions selected by the user for future use with technical support to help expedite troubleshooting.
 16. The system of claim 11, wherein if the user's voice control request has not been resolved, the system provides escalation paths that include one or more of: present a customer support phone number, present a customer support email address, and offer to connect the user with a live agent.
 17. The system of claim 11, further comprising a context manager that manages permissions, wherein the permissions control the visibility of available control and support pathways to the user and category visibility to the user.
 18. The system of claim 11, further comprising a context manager that manages logic sets, wherein the logic sets control action visibility to the user.
 19. The system of claim 11, further comprising a front end user interface that enables users to identify an appropriate control and support pathway that addresses a current issue of interest to the user via browsing a list of available control and support pathways to the user.
 20. A method for context-driven voice-control using an application control interface, the method comprising: enabling a user to initiate a voice control session; gathering user attributes for use in the voice control session; receiving voice control requests from a user during the voice control session; executing a search and dynamically generating control and support pathways that are available to a user based on the user attributes; presenting a list of available control and support pathways to a user based on the user attributes; receiving a vocal selection, by the user, of an available control and support pathway; after the available control and support pathways is vocally selected, presenting stages sequentially to the user, each stage having a list of actions that the user can select; in response to receiving a vocal selection of an action in the voice control session, updating the stages sequentially presented to the user in the available control and support pathways; and in response to receiving a vocal selection of an action in the voice control session, sending an authorization signal via an external system to perform a function related to the vocally selected action.
 21. The method of claim 20, further comprising: enabling users to control customer service activities related to live broadcast programming, recorded programming, streaming programming, and on-demand programming using vocal selection by the user.
 22. The method of claim 20, further comprising: enabling users to control account management activities using vocal selection by the user.
 23. The method of claim 20, further comprising: enabling users to control authentication to authorize changes to their account using vocal selection by the user.
 24. The method of claim 20, further comprising: enabling users to control troubleshooting of equipment and system capabilities using vocal selection by the user. 